fix: restore ARGUS feed route aliases#46
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
argus | dd82f15 | Jun 08 2026, 01:04 AM |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: dd82f1579f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| return NextResponse.json({ error: "AISSTREAM_API_KEY not configured" }, { status: 500 }); | ||
| const message = "AISSTREAM_API_KEY not configured"; | ||
| reportFeedHealth("aisstream", "error", message); | ||
| return NextResponse.json({ vessels: [], _degraded: true, _source: "ais-empty", _reason: message }); |
There was a problem hiding this comment.
When AISSTREAM_API_KEY is unset, this now returns HTTP 200 with an empty vessels array even though the server records an error. The existing client only throws on non-OK responses in argus-app/src/lib/ingest/aisstream.ts:23-25, so the polling path in CesiumGlobe.tsx:1783-1786 will treat the missing credential as a successful AIS refresh and mark the feed healthy with zero vessels. Please keep a non-2xx status here or update the client to treat _degraded as a feed error/degraded state.
Useful? React with 👍 / 👎.
1 participant
Summary
Test Plan
Notes